fix: pin host-adapter hook content before execution - #173
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #131. Adds manifest-declared hook-file validation, combined manifest-plus-file content hashing, consent/grant invalidation on content drift, and fail-closed re-verification immediately before lifecycle or execution spawns. Includes adapter integrity, admission, execution, conformance, lifecycle, CLI, documentation, and ADR coverage. Validation passed: typecheck, lint, markdown lint, build, and targeted adapter suites. The full local check has one environment-specific failure because the stock OpenCode acceptance test exact-pins 1.18.18 while the current npm-global/latest release is 1.18.22; this is tracked in #172. Keep #131 open until this replacement is reviewed, CI-green, and merged; then close #131 as superseded.